Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d69eb21a5398bef7ec430e358a7b552832977a90846ef3db397497a362fac3a7

Tx prefix hash: 17102d8a6997b06f0165979c33de3d2a8501fdb097bad2133ed95682be5fe3af
Tx public key: 6c8fab955d20f44b77a8d62f1bf9e1c8be68be2caf3b1728b3d9647ffdbf6ef4
Timestamp: 1717266964 Timestamp [UCT]: 2024-06-01 18:36:04 Age [y:d:h:m:s]: 01:161:07:37:19
Block: 1034904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373869 RingCT/type: yes/0
Extra: 016c8fab955d20f44b77a8d62f1bf9e1c8be68be2caf3b1728b3d9647ffdbf6ef402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03fd06c2380c7b5b3bb0c88de1b088cee7af7284e0181ac53598004ebbda78b5 0.600000000000 1503423 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": 1034914, "vin": [ { "gen": { "height": 1034904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03fd06c2380c7b5b3bb0c88de1b088cee7af7284e0181ac53598004ebbda78b5" } } ], "extra": [ 1, 108, 143, 171, 149, 93, 32, 244, 75, 119, 168, 214, 47, 27, 249, 225, 200, 190, 104, 190, 44, 175, 59, 23, 40, 179, 217, 100, 127, 253, 191, 110, 244, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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