Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02af2ca00661c140feda92ebd6034c53f2fe289f3a09a122ab2a7ebffde4acc5

Tx prefix hash: bffd563df6c6ca27fbd6f86ac9ef6f7248a9b9f6227cf56c2a75eba6309e2788
Tx public key: d9495be1d210dede3aaf8a8247b720da6e780ccda541ad529e70e5e1a95979f3
Timestamp: 1750995210 Timestamp [UCT]: 2025-06-27 03:33:30 Age [y:d:h:m:s]: 00:136:03:58:27
Block: 1313610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95326 RingCT/type: yes/0
Extra: 01d9495be1d210dede3aaf8a8247b720da6e780ccda541ad529e70e5e1a95979f30211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b950be4fe60a4b3da7538d7986c937dcb6b51e77eeb70373c76f10abf38065d1 0.600000000000 1801251 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": 1313620, "vin": [ { "gen": { "height": 1313610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b950be4fe60a4b3da7538d7986c937dcb6b51e77eeb70373c76f10abf38065d1" } } ], "extra": [ 1, 217, 73, 91, 225, 210, 16, 222, 222, 58, 175, 138, 130, 71, 183, 32, 218, 110, 120, 12, 205, 165, 65, 173, 82, 158, 112, 229, 225, 169, 89, 121, 243, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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