Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efc7e679f4aaf487a2eb0e1cd79ad0624dc2b6e32858b0c1bf7951d5fdf57b64

Tx prefix hash: f5936f8a25ee66f79f83c609222362073595ff5b073e8062227fca396d86b4a2
Tx public key: d9447fa075d51aae5457f3ddea12e14de4af4488d1bcf2a3dd621c85b5ef4992
Timestamp: 1583859146 Timestamp [UCT]: 2020-03-10 16:52:26 Age [y:d:h:m:s]: 04:255:19:40:16
Block: 80079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1077737 RingCT/type: yes/0
Extra: 01d9447fa075d51aae5457f3ddea12e14de4af4488d1bcf2a3dd621c85b5ef49920211000000064ac5aa02000000000000000000

1 output(s) for total of 333.169947547000 dcy

stealth address amount amount idx
00: 782b14c293b18b839a510013a5c258ff77d7b44dbd078e1b10e66a164a8166b9 333.169947547000 146515 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": 80089, "vin": [ { "gen": { "height": 80079 } } ], "vout": [ { "amount": 333169947547, "target": { "key": "782b14c293b18b839a510013a5c258ff77d7b44dbd078e1b10e66a164a8166b9" } } ], "extra": [ 1, 217, 68, 127, 160, 117, 213, 26, 174, 84, 87, 243, 221, 234, 18, 225, 77, 228, 175, 68, 136, 209, 188, 242, 163, 221, 98, 28, 133, 181, 239, 73, 146, 2, 17, 0, 0, 0, 6, 74, 197, 170, 2, 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