Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 725bd42e95c013d9ee2a22c5b169f5082176bc90714ad32bd88fc9a189c42a71

Tx prefix hash: fbdf99d071787f94bef2519ae68151a520a02c812da3dabceb6283c20be0c4ea
Tx public key: 572ea1559b1bac3906a28361c5f0210a7f5234602587c8188511a8331b23df5c
Timestamp: 1581158696 Timestamp [UCT]: 2020-02-08 10:44:56 Age [y:d:h:m:s]: 04:323:02:15:12
Block: 60838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122790 RingCT/type: yes/0
Extra: 01572ea1559b1bac3906a28361c5f0210a7f5234602587c8188511a8331b23df5c0211000000288a2ee0d9000000000000000000

1 output(s) for total of 385.850678300000 dcy

stealth address amount amount idx
00: a170ffb34a4056959f46360876b067e046e42c443ed4a56adf7ae171bc65e2e6 385.850678300000 112099 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": 60848, "vin": [ { "gen": { "height": 60838 } } ], "vout": [ { "amount": 385850678300, "target": { "key": "a170ffb34a4056959f46360876b067e046e42c443ed4a56adf7ae171bc65e2e6" } } ], "extra": [ 1, 87, 46, 161, 85, 155, 27, 172, 57, 6, 162, 131, 97, 197, 240, 33, 10, 127, 82, 52, 96, 37, 135, 200, 24, 133, 17, 168, 51, 27, 35, 223, 92, 2, 17, 0, 0, 0, 40, 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