Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2989a5b1fb4be5dbe2a715aa09e308c16eff5add807892298ebbaa10a2cdca39

Tx prefix hash: 04f632eb227622cb407026af1b4c084863a3ebd93c74142507ae05e28fe751a0
Tx public key: 57afd839813c87f054d6249532ce581b31e5c863e1c70f622def6c5ed7af2a4f
Timestamp: 1724370442 Timestamp [UCT]: 2024-08-22 23:47:22 Age [y:d:h:m:s]: 00:217:03:37:12
Block: 1093802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155037 RingCT/type: yes/0
Extra: 0157afd839813c87f054d6249532ce581b31e5c863e1c70f622def6c5ed7af2a4f021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3f14b5a0c510177788cc6be77c54ee94362410b935ea48fbac4d55013290660 0.600000000000 1568819 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": 1093812, "vin": [ { "gen": { "height": 1093802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3f14b5a0c510177788cc6be77c54ee94362410b935ea48fbac4d55013290660" } } ], "extra": [ 1, 87, 175, 216, 57, 129, 60, 135, 240, 84, 214, 36, 149, 50, 206, 88, 27, 49, 229, 200, 99, 225, 199, 15, 98, 45, 239, 108, 94, 215, 175, 42, 79, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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