Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae964bd33cf04b296f2b11299b8079d489af4dadb87d8be3b9bbced88c034fe3

Tx prefix hash: 321b4f115c6b197ce88f06a6fc501435d6c23443fa8500f0942436174a5f4f54
Tx public key: 12d59373e134cc2b5b5915f7f885b0b673f86f8109dbdf1c9518333eb4c8b22c
Timestamp: 1707365617 Timestamp [UCT]: 2024-02-08 04:13:37 Age [y:d:h:m:s]: 01:130:21:46:17
Block: 952799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354539 RingCT/type: yes/0
Extra: 0112d59373e134cc2b5b5915f7f885b0b673f86f8109dbdf1c9518333eb4c8b22c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73ccbd7232a594f005fbf2bf425ddc8a5c3ad5af67ffc0d73fbee56253314fd7 0.600000000000 1411931 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": 952809, "vin": [ { "gen": { "height": 952799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73ccbd7232a594f005fbf2bf425ddc8a5c3ad5af67ffc0d73fbee56253314fd7" } } ], "extra": [ 1, 18, 213, 147, 115, 225, 52, 204, 43, 91, 89, 21, 247, 248, 133, 176, 182, 115, 248, 111, 129, 9, 219, 223, 28, 149, 24, 51, 62, 180, 200, 178, 44, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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