Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 955250565ac3bceb37527b41e7bcdf7dc0a4ee4e5da1892d871b1fe1fe495c4d

Tx prefix hash: bfa1cb33b73e2c4821bf46374d0b8982e1c99865c867a3035cf729f1a3cfffd0
Tx public key: a454351698ae21ede1a965cf3c237681ae46f806968a0b3816177c5e3bc38389
Timestamp: 1734472220 Timestamp [UCT]: 2024-12-17 21:50:20 Age [y:d:h:m:s]: 00:098:16:43:43
Block: 1177449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70286 RingCT/type: yes/0
Extra: 01a454351698ae21ede1a965cf3c237681ae46f806968a0b3816177c5e3bc383890211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87f33a6a19d27197d5d204a76b5c82429e0bf4ff2efbf71846baf8d5a43dec30 0.600000000000 1663820 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": 1177459, "vin": [ { "gen": { "height": 1177449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87f33a6a19d27197d5d204a76b5c82429e0bf4ff2efbf71846baf8d5a43dec30" } } ], "extra": [ 1, 164, 84, 53, 22, 152, 174, 33, 237, 225, 169, 101, 207, 60, 35, 118, 129, 174, 70, 248, 6, 150, 138, 11, 56, 22, 23, 124, 94, 59, 195, 131, 137, 2, 17, 0, 0, 0, 7, 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