Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b603bf48fadf27ce984ab2a3cb623d45d734abbf1777204bcf51c9746e242aa

Tx prefix hash: e5cdbed3ddbc0808cdb23b8c7f6c3d7af3fe468092b0cadc6006b58b02f8bca5
Tx public key: 8e22e71cfd076c8ef98a7b9172a2636fd932bc7c289e6f6383e8cf0f2f643291
Timestamp: 1702253628 Timestamp [UCT]: 2023-12-11 00:13:48 Age [y:d:h:m:s]: 01:333:21:35:51
Block: 910430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497490 RingCT/type: yes/0
Extra: 018e22e71cfd076c8ef98a7b9172a2636fd932bc7c289e6f6383e8cf0f2f64329102110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c31907e8f1cc7c11bfc6c9bfef5c135b1eba1b2cea91274c1cb0c3d331a10ee9 0.600000000000 1367587 of 15

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": 910440, "vin": [ { "gen": { "height": 910430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c31907e8f1cc7c11bfc6c9bfef5c135b1eba1b2cea91274c1cb0c3d331a10ee9" } } ], "extra": [ 1, 142, 34, 231, 28, 253, 7, 108, 142, 249, 138, 123, 145, 114, 162, 99, 111, 217, 50, 188, 124, 40, 158, 111, 99, 131, 232, 207, 15, 47, 100, 50, 145, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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