Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd0aec74e91e4733b60361a03c287d58987adc6604124b96deecadda59847c6d

Tx prefix hash: 0c9afbc24fe501efc5d1f493f9fdccc32dc3590a448db254d8b6ee594db4a61b
Tx public key: 0eceb3f2d9ce1e1da0605129a7d43d1b30ea093a1ab43588cea3129d6fd034e1
Timestamp: 1578090310 Timestamp [UCT]: 2020-01-03 22:25:10 Age [y:d:h:m:s]: 05:060:21:44:03
Block: 38038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1193425 RingCT/type: yes/0
Extra: 010eceb3f2d9ce1e1da0605129a7d43d1b30ea093a1ab43588cea3129d6fd034e102110000000d8a2ee0d9000000000000000000

1 output(s) for total of 459.161183039000 dcy

stealth address amount amount idx
00: 29f03847b8f24aa3b49119f23d4d5ed35765e272c80a717b558c903eb3e9a77b 459.161183039000 64685 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": 38048, "vin": [ { "gen": { "height": 38038 } } ], "vout": [ { "amount": 459161183039, "target": { "key": "29f03847b8f24aa3b49119f23d4d5ed35765e272c80a717b558c903eb3e9a77b" } } ], "extra": [ 1, 14, 206, 179, 242, 217, 206, 30, 29, 160, 96, 81, 41, 167, 212, 61, 27, 48, 234, 9, 58, 26, 180, 53, 136, 206, 163, 18, 157, 111, 208, 52, 225, 2, 17, 0, 0, 0, 13, 138, 46, 224, 217, 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