Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a01116ea85223a0c124ddf722add324c5a96190b36ff56aa0b5b9130046d8b54

Tx prefix hash: 59d4566833ec5a4fd7fcf0dbc0609b778b3823206f277c5a5e86e82fc88de3cd
Tx public key: 73a4935f434fde02e2baf819e347fb6e766df1845cd5401f0db258a0359c0dfb
Timestamp: 1733461315 Timestamp [UCT]: 2024-12-06 05:01:55 Age [y:d:h:m:s]: 00:100:17:31:33
Block: 1169048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71803 RingCT/type: yes/0
Extra: 0173a4935f434fde02e2baf819e347fb6e766df1845cd5401f0db258a0359c0dfb021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06be2a5e1a41549d6730ce408c40380f6343420fe4b58fbdc1d04e16c6785501 0.600000000000 1654761 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": 1169058, "vin": [ { "gen": { "height": 1169048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06be2a5e1a41549d6730ce408c40380f6343420fe4b58fbdc1d04e16c6785501" } } ], "extra": [ 1, 115, 164, 147, 95, 67, 79, 222, 2, 226, 186, 248, 25, 227, 71, 251, 110, 118, 109, 241, 132, 92, 213, 64, 31, 13, 178, 88, 160, 53, 156, 13, 251, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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