Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e04cc1e13e2421a1d00c9fb64b7a935dbb0bb8e71fca77b2c1174d93889d7f38

Tx prefix hash: 729b40447b18c0989a9a0c6b637f46d848ad2c16a8d74fc9d5b6d5b91ec80c40
Tx public key: 7dd035e8842a4caa7d0832c92f254adeac107929fcfba457b029fa410d4503f8
Timestamp: 1581085259 Timestamp [UCT]: 2020-02-07 14:20:59 Age [y:d:h:m:s]: 05:245:10:58:57
Block: 60292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1325545 RingCT/type: yes/0
Extra: 017dd035e8842a4caa7d0832c92f254adeac107929fcfba457b029fa410d4503f802110000000156c366d3000000000000000000

1 output(s) for total of 387.461355526000 dcy

stealth address amount amount idx
00: 59b47df37eff8bb7da1dc3a59d0ebdeb83d54edc2314b19c78cc2c8dd0d6e846 387.461355526000 111180 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": 60302, "vin": [ { "gen": { "height": 60292 } } ], "vout": [ { "amount": 387461355526, "target": { "key": "59b47df37eff8bb7da1dc3a59d0ebdeb83d54edc2314b19c78cc2c8dd0d6e846" } } ], "extra": [ 1, 125, 208, 53, 232, 132, 42, 76, 170, 125, 8, 50, 201, 47, 37, 74, 222, 172, 16, 121, 41, 252, 251, 164, 87, 176, 41, 250, 65, 13, 69, 3, 248, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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