Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb2891fd9d34dc50771b8b53d565850569c69d1b4979a5fd2a22398418cd78df

Tx prefix hash: 125aa6b99aa8e203c1dbbaade47a362f299617ea964f97f1d5b4fac850143925
Tx public key: 8bcb641dd56b5cf7e447d6ccb8250fc039c53aaec3baa2902b9d0bfd84737971
Timestamp: 1741251745 Timestamp [UCT]: 2025-03-06 09:02:25 Age [y:d:h:m:s]: 00:260:00:32:53
Block: 1233283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183573 RingCT/type: yes/0
Extra: 018bcb641dd56b5cf7e447d6ccb8250fc039c53aaec3baa2902b9d0bfd84737971021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8b72492101a9edf20149722024c533171c2aa95e5f42313de2f7697de932f8e 0.600000000000 1720202 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": 1233293, "vin": [ { "gen": { "height": 1233283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8b72492101a9edf20149722024c533171c2aa95e5f42313de2f7697de932f8e" } } ], "extra": [ 1, 139, 203, 100, 29, 213, 107, 92, 247, 228, 71, 214, 204, 184, 37, 15, 192, 57, 197, 58, 174, 195, 186, 162, 144, 43, 157, 11, 253, 132, 115, 121, 113, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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