Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a2a3570cb6daf2a5c3fcbeeb48d073f2a18355bccdda90b38c06f388d667b98a

Tx prefix hash: f8e8d51435abbea39c00e87e204db08c630b60a2cb077047dd2d96f0bdecc6a7
Tx public key: f35a553e09859d6854e8075d9dc5a3cfedcbc27dbebc15e26b707964c14b85e7
Timestamp: 1757500225 Timestamp [UCT]: 2025-09-10 10:30:25 Age [y:d:h:m:s]: 00:136:15:21:22
Block: 1365365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97638 RingCT/type: yes/0
Extra: 01f35a553e09859d6854e8075d9dc5a3cfedcbc27dbebc15e26b707964c14b85e702110000001bad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57f76f4c26e27ef3ca7455caf5476edd054541042d67429b8cc530f42cf4e1ac 0.600000000000 1853404 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1365375, "vin": [ { "gen": { "height": 1365365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57f76f4c26e27ef3ca7455caf5476edd054541042d67429b8cc530f42cf4e1ac" } } ], "extra": [ 1, 243, 90, 85, 62, 9, 133, 157, 104, 84, 232, 7, 93, 157, 197, 163, 207, 237, 203, 194, 125, 190, 188, 21, 226, 107, 112, 121, 100, 193, 75, 133, 231, 2, 17, 0, 0, 0, 27, 173, 121, 72, 208, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8