Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d95790411c4b1d3be5bc81a3e4f9926aa025e5f51eb17d5a9288a7e398ce73eb

Tx prefix hash: 95f7ec2c407b6b104203ebdc8682ddd5101291191bbd6d40bdb1b9232b823028
Tx public key: 94142c8285da75020ecb77a8e8cc45bb284066c823c2f7ed639e94cc2e2d659e
Timestamp: 1737466516 Timestamp [UCT]: 2025-01-21 13:35:16 Age [y:d:h:m:s]: 00:303:14:02:51
Block: 1202166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214512 RingCT/type: yes/0
Extra: 0194142c8285da75020ecb77a8e8cc45bb284066c823c2f7ed639e94cc2e2d659e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0490a6e63577a69316c60987854c5024ae5f7afc870a4178521e1b263d3b6f37 0.600000000000 1688827 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": 1202176, "vin": [ { "gen": { "height": 1202166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0490a6e63577a69316c60987854c5024ae5f7afc870a4178521e1b263d3b6f37" } } ], "extra": [ 1, 148, 20, 44, 130, 133, 218, 117, 2, 14, 203, 119, 168, 232, 204, 69, 187, 40, 64, 102, 200, 35, 194, 247, 237, 99, 158, 148, 204, 46, 45, 101, 158, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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