Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 616985a7d3d32e8a70609d5f277117f71fbccc84add7a06fca31b04ea833b3c6

Tx prefix hash: b6baf2ff937ef88df0068e12c89451a8df14033ebe1ab702e8e22bf06a729371
Tx public key: 8d3753cf167304b5da66c3275309d2c779f7fa1e19e8da3fbeb9f72daa1e82f8
Timestamp: 1764510223 Timestamp [UCT]: 2025-11-30 13:43:43 Age [y:d:h:m:s]: 00:000:03:48:24
Block: 1423439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118 RingCT/type: yes/0
Extra: 018d3753cf167304b5da66c3275309d2c779f7fa1e19e8da3fbeb9f72daa1e82f8021100000003defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d4bbe04827946347facfcde38a0ad4716834405b7f07d09b2fe3822b3cdd943 0.600000000000 1912052 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": 1423449, "vin": [ { "gen": { "height": 1423439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d4bbe04827946347facfcde38a0ad4716834405b7f07d09b2fe3822b3cdd943" } } ], "extra": [ 1, 141, 55, 83, 207, 22, 115, 4, 181, 218, 102, 195, 39, 83, 9, 210, 199, 121, 247, 250, 30, 25, 232, 218, 63, 190, 185, 247, 45, 170, 30, 130, 248, 2, 17, 0, 0, 0, 3, 222, 251, 143, 24, 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