Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a31b86030c0f0c6b04dcaa142d9fbf98a59968c139ec89ebe31c28490d5bdcc

Tx prefix hash: 29b20bfdcc3f60cee9a2b4c858334681da6f0a440fe4bfa8ffb7da5c5bcc1a0c
Tx public key: 0f44bab5e42660ff483e44ce0984d0bf72e2225b3a9b79a301fdfc1508262148
Timestamp: 1729691533 Timestamp [UCT]: 2024-10-23 13:52:13 Age [y:d:h:m:s]: 00:140:21:21:40
Block: 1137871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100498 RingCT/type: yes/0
Extra: 010f44bab5e42660ff483e44ce0984d0bf72e2225b3a9b79a301fdfc15082621480211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a2a909dcd61701a3d5e3e2e3c75818d5da7bd445f26b01e0e112f905533db5f 0.600000000000 1621450 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": 1137881, "vin": [ { "gen": { "height": 1137871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a2a909dcd61701a3d5e3e2e3c75818d5da7bd445f26b01e0e112f905533db5f" } } ], "extra": [ 1, 15, 68, 186, 181, 228, 38, 96, 255, 72, 62, 68, 206, 9, 132, 208, 191, 114, 226, 34, 91, 58, 155, 121, 163, 1, 253, 252, 21, 8, 38, 33, 72, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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