Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0156c4c5c1037e1eb6fd91c650ce61c59b8c7f64e2ce063af905212c1233929a

Tx prefix hash: 9bc7fa898023e7edb661d86e1728e55e4cc8c002fa655a21fe4a41a8225e92f9
Tx public key: bd95c350167dbcd9fe0c8f5498da0a6255af17fd4f3a43d7d12d0f0f51b62302
Timestamp: 1740632763 Timestamp [UCT]: 2025-02-27 05:06:03 Age [y:d:h:m:s]: 00:267:18:55:49
Block: 1228140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189154 RingCT/type: yes/0
Extra: 01bd95c350167dbcd9fe0c8f5498da0a6255af17fd4f3a43d7d12d0f0f51b6230202110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bc8df4d6975002dadd565efe48d4511e8fc824cf00b4312b6728aad7b823973 0.600000000000 1715017 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": 1228150, "vin": [ { "gen": { "height": 1228140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bc8df4d6975002dadd565efe48d4511e8fc824cf00b4312b6728aad7b823973" } } ], "extra": [ 1, 189, 149, 195, 80, 22, 125, 188, 217, 254, 12, 143, 84, 152, 218, 10, 98, 85, 175, 23, 253, 79, 58, 67, 215, 209, 45, 15, 15, 81, 182, 35, 2, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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