Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae55285f2a474d0d326816a9047d8b0acef9f8440d91e9db7f9c8fa600c2bbee

Tx prefix hash: 453e843e8dadfb1cec4ca03d2f0af1e0217326d7473b30d82d527409b5f371a7
Tx public key: e92ef152ef557ad447fd85832afd55adbc324c86f1ce5abf894df5480c504fad
Timestamp: 1702053031 Timestamp [UCT]: 2023-12-08 16:30:31 Age [y:d:h:m:s]: 01:083:03:22:00
Block: 908762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320542 RingCT/type: yes/0
Extra: 01e92ef152ef557ad447fd85832afd55adbc324c86f1ce5abf894df5480c504fad02110000000433af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b58932ac625e4c1de7e7f32258bb203f201d82237c95cf32bf2a62adc17b1e1b 0.600000000000 1365817 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": 908772, "vin": [ { "gen": { "height": 908762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b58932ac625e4c1de7e7f32258bb203f201d82237c95cf32bf2a62adc17b1e1b" } } ], "extra": [ 1, 233, 46, 241, 82, 239, 85, 122, 212, 71, 253, 133, 131, 42, 253, 85, 173, 188, 50, 76, 134, 241, 206, 90, 191, 137, 77, 245, 72, 12, 80, 79, 173, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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