Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a0d2f3d1d50d94f96507eee6f1feb7ce779847d1b29feb523f0ee45076c39b5

Tx prefix hash: 32a1c311ff0957e5c70bc47298431fc0a05215a30fbea9b871339c2b45cafc5f
Tx public key: 57289309738c2df15e559f630e92e701b76677f527331fc2aa71d7065c2e2472
Timestamp: 1698501347 Timestamp [UCT]: 2023-10-28 13:55:47 Age [y:d:h:m:s]: 01:182:11:41:54
Block: 879538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391432 RingCT/type: yes/0
Extra: 0157289309738c2df15e559f630e92e701b76677f527331fc2aa71d7065c2e2472021100000002faf35c9c000000000000000000

1 output(s) for total of 0.747696772000 dcy

stealth address amount amount idx
00: 672fe05d42db32fa622627dd4deb059014957365f2415c289692a951681e5ff3 0.747696772000 1335066 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": 879548, "vin": [ { "gen": { "height": 879538 } } ], "vout": [ { "amount": 747696772, "target": { "key": "672fe05d42db32fa622627dd4deb059014957365f2415c289692a951681e5ff3" } } ], "extra": [ 1, 87, 40, 147, 9, 115, 140, 45, 241, 94, 85, 159, 99, 14, 146, 231, 1, 183, 102, 119, 245, 39, 51, 31, 194, 170, 113, 215, 6, 92, 46, 36, 114, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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