Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbee9ab9dc2067615c6462c1c5257c7939317b51d9d6a5641ad809037a0c1cd3

Tx prefix hash: 71a228876022d9b254582862d807a9ee76ce142d0dd609fb604d277240fdba8e
Tx public key: e4781dbaac576e1bf3410dcb11f117fbb39ed09babf6b3d89227921b3aa1a6f4
Timestamp: 1648255333 Timestamp [UCT]: 2022-03-26 00:42:13 Age [y:d:h:m:s]: 02:354:15:10:39
Block: 466454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 772774 RingCT/type: yes/0
Extra: 01e4781dbaac576e1bf3410dcb11f117fbb39ed09babf6b3d89227921b3aa1a6f402110000000606faf294000000000000000000

1 output(s) for total of 17.476099890000 dcy

stealth address amount amount idx
00: 6524410e673ab558ab7e0b7b3923dbe3ca2ee067829cf7a26ae439962ef25fd1 17.476099890000 884773 of 0

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": 466464, "vin": [ { "gen": { "height": 466454 } } ], "vout": [ { "amount": 17476099890, "target": { "key": "6524410e673ab558ab7e0b7b3923dbe3ca2ee067829cf7a26ae439962ef25fd1" } } ], "extra": [ 1, 228, 120, 29, 186, 172, 87, 110, 27, 243, 65, 13, 203, 17, 241, 23, 251, 179, 158, 208, 155, 171, 246, 179, 216, 146, 39, 146, 27, 58, 161, 166, 244, 2, 17, 0, 0, 0, 6, 6, 250, 242, 148, 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