Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3a8d5d75cde3fc9926217c8c9dbef878d59e2713a3144baa812eff81900f91a

Tx prefix hash: a611492e5fe90d9b110bec25b0adc6bf8654655dfd1d621be7ea911bb29b835b
Tx public key: 3ada11259bd0f2a31a47ec46a98c978682869a9c8d037f68e868bb68c5a8a37a
Timestamp: 1735865820 Timestamp [UCT]: 2025-01-03 00:57:00 Age [y:d:h:m:s]: 00:098:18:24:33
Block: 1188957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70384 RingCT/type: yes/0
Extra: 013ada11259bd0f2a31a47ec46a98c978682869a9c8d037f68e868bb68c5a8a37a02110000000625a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee9fbf0982af623b57f0d00efd4dafeac51238c845db3921cad8a3b40de8da09 0.600000000000 1675462 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": 1188967, "vin": [ { "gen": { "height": 1188957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee9fbf0982af623b57f0d00efd4dafeac51238c845db3921cad8a3b40de8da09" } } ], "extra": [ 1, 58, 218, 17, 37, 155, 208, 242, 163, 26, 71, 236, 70, 169, 140, 151, 134, 130, 134, 154, 156, 141, 3, 127, 104, 232, 104, 187, 104, 197, 168, 163, 122, 2, 17, 0, 0, 0, 6, 37, 163, 90, 15, 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