Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50e86fca1ea51c324c3a7f9c5bf63fb1d95707e1c3340760a051ab8e19f7286e

Tx prefix hash: ccabf89acc2161cb10b25469bba173d2af4814ff1bfae7bb8dc3dc4cffc36b8c
Tx public key: ea1d15645fd0e806853bd5d5492880f9917a082cb1fa1def8cfe66bc0f676ade
Timestamp: 1637828213 Timestamp [UCT]: 2021-11-25 08:16:53 Age [y:d:h:m:s]: 03:340:22:19:04
Block: 381696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1020058 RingCT/type: yes/0
Extra: 01ea1d15645fd0e806853bd5d5492880f9917a082cb1fa1def8cfe66bc0f676ade021100000002e9564d6f000000000000000000

1 output(s) for total of 33.364381674000 dcy

stealth address amount amount idx
00: b7ebf7351eec89de96d361424dc1b7c3e4a7c0c7491043ba2d7ee3d81f74e3f3 33.364381674000 771034 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": 381706, "vin": [ { "gen": { "height": 381696 } } ], "vout": [ { "amount": 33364381674, "target": { "key": "b7ebf7351eec89de96d361424dc1b7c3e4a7c0c7491043ba2d7ee3d81f74e3f3" } } ], "extra": [ 1, 234, 29, 21, 100, 95, 208, 232, 6, 133, 59, 213, 213, 73, 40, 128, 249, 145, 122, 8, 44, 177, 250, 29, 239, 140, 254, 102, 188, 15, 103, 106, 222, 2, 17, 0, 0, 0, 2, 233, 86, 77, 111, 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