Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5801b23ad7e4ccd1957a18571dff9b30112845ade50751c612d7ecce018155e

Tx prefix hash: c63dbe05101a41957ffd3b75f2571a1a72acbc273eaf4e62f7828765400ef0ac
Tx public key: c49914b5f6122eddf3b77e0c280e4b0e8a8da93a2d8110533f8d9cde2d2fd733
Timestamp: 1580793462 Timestamp [UCT]: 2020-02-04 05:17:42 Age [y:d:h:m:s]: 04:328:05:47:53
Block: 58375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125881 RingCT/type: yes/0
Extra: 01c49914b5f6122eddf3b77e0c280e4b0e8a8da93a2d8110533f8d9cde2d2fd73302110000000149b77a3d000000000000000000

1 output(s) for total of 393.180955683000 dcy

stealth address amount amount idx
00: 10f0b16527f17d7d4b90f7e4dee9c131fc6f014d78204ccbf9db4b4f3c0c24c3 393.180955683000 107853 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": 58385, "vin": [ { "gen": { "height": 58375 } } ], "vout": [ { "amount": 393180955683, "target": { "key": "10f0b16527f17d7d4b90f7e4dee9c131fc6f014d78204ccbf9db4b4f3c0c24c3" } } ], "extra": [ 1, 196, 153, 20, 181, 246, 18, 46, 221, 243, 183, 126, 12, 40, 14, 75, 14, 138, 141, 169, 58, 45, 129, 16, 83, 63, 141, 156, 222, 45, 47, 215, 51, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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