Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 847d3e0e6b44d45688503d5b10b841991fc9ebd7f2d09b652c55e7cf9ad88c92

Tx prefix hash: b41056c4fb3d96a27f05f2fc2c0cf53756db65c1a128c669ad14f7ee88f9c67c
Tx public key: 5f83a7a79ca0aa5edf722d7c33b222763ce6e408a9ba0bf669a9ca7a9f738ef2
Timestamp: 1577737065 Timestamp [UCT]: 2019-12-30 20:17:45 Age [y:d:h:m:s]: 05:062:18:20:19
Block: 35305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1194554 RingCT/type: yes/0
Extra: 015f83a7a79ca0aa5edf722d7c33b222763ce6e408a9ba0bf669a9ca7a9f738ef20211000000074943cd9f000000000000000000

1 output(s) for total of 468.835764361000 dcy

stealth address amount amount idx
00: 65f3a4be8f044e2132acd9a87db2a8714459915cd45f04408ec53debb0900379 468.835764361000 59466 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": 35315, "vin": [ { "gen": { "height": 35305 } } ], "vout": [ { "amount": 468835764361, "target": { "key": "65f3a4be8f044e2132acd9a87db2a8714459915cd45f04408ec53debb0900379" } } ], "extra": [ 1, 95, 131, 167, 167, 156, 160, 170, 94, 223, 114, 45, 124, 51, 178, 34, 118, 60, 230, 228, 8, 169, 186, 11, 246, 105, 169, 202, 122, 159, 115, 142, 242, 2, 17, 0, 0, 0, 7, 73, 67, 205, 159, 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