Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86346dd41fcbc785256f49246c7f5b61ab49323b1a1bf991d2ac23fda47a80a3

Tx prefix hash: d9841a86b7bb6614066b77c0ab51c562cae0aa3926269629eafb04bcf4d2b734
Tx public key: dee4e92c820928e836fb373bff196ec4127d32fb9b194683b57bfe9f3419ca2b
Timestamp: 1715568341 Timestamp [UCT]: 2024-05-13 02:45:41 Age [y:d:h:m:s]: 00:331:12:08:34
Block: 1020838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236933 RingCT/type: yes/0
Extra: 01dee4e92c820928e836fb373bff196ec4127d32fb9b194683b57bfe9f3419ca2b02110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a84520e9111d44b6d7daeac7659c17a4923cf1aaf3b2555090f126a1ed6a701 0.600000000000 1484947 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": 1020848, "vin": [ { "gen": { "height": 1020838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a84520e9111d44b6d7daeac7659c17a4923cf1aaf3b2555090f126a1ed6a701" } } ], "extra": [ 1, 222, 228, 233, 44, 130, 9, 40, 232, 54, 251, 55, 59, 255, 25, 110, 196, 18, 125, 50, 251, 155, 25, 70, 131, 181, 123, 254, 159, 52, 25, 202, 43, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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