Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f2d8930aa0ee59c362a0ba5236d3dc4650f10e6c74f7c4f359db1bb1a1a0dbb

Tx prefix hash: 5d86f7b433a386fe740285496f52da90bb5705b38bd69da8ccba0fa3326a41d1
Tx public key: 6718769a6bfc0e051aae7400e18c50221ab99e15f1831fd6a04cfee515b60496
Timestamp: 1743912984 Timestamp [UCT]: 2025-04-06 04:16:24 Age [y:d:h:m:s]: 00:279:16:13:29
Block: 1255308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197702 RingCT/type: yes/0
Extra: 016718769a6bfc0e051aae7400e18c50221ab99e15f1831fd6a04cfee515b60496021100000012dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1605d5e95f9915e5f0103c3e088ec953949eafecbd3937e21a51d1166d2325af 0.600000000000 1742411 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": 1255318, "vin": [ { "gen": { "height": 1255308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1605d5e95f9915e5f0103c3e088ec953949eafecbd3937e21a51d1166d2325af" } } ], "extra": [ 1, 103, 24, 118, 154, 107, 252, 14, 5, 26, 174, 116, 0, 225, 140, 80, 34, 26, 185, 158, 21, 241, 131, 31, 214, 160, 76, 254, 229, 21, 182, 4, 150, 2, 17, 0, 0, 0, 18, 219, 181, 113, 193, 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