Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a2db384bd64b51da2ccfc5254ddbddaee73647f45b7b8b56182508a69a1715d

Tx prefix hash: a8c4fb32facd55e3df141a91149277dca6021ad567bc730c9aaf747d419e5e13
Tx public key: 06e48af8af8e5b36c014de1c30f3934c90f9578f246f5c9315734559c81422f8
Timestamp: 1675451647 Timestamp [UCT]: 2023-02-03 19:14:07 Age [y:d:h:m:s]: 01:346:11:41:16
Block: 689108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508607 RingCT/type: yes/0
Extra: 0106e48af8af8e5b36c014de1c30f3934c90f9578f246f5c9315734559c81422f80211000000015029cbac000000000000000000

1 output(s) for total of 3.196679257000 dcy

stealth address amount amount idx
00: ded03bc70705801e8b13162c585f27a4fd75574df8ff69e1f4a166a127698cd5 3.196679257000 1131772 of 0

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": 689118, "vin": [ { "gen": { "height": 689108 } } ], "vout": [ { "amount": 3196679257, "target": { "key": "ded03bc70705801e8b13162c585f27a4fd75574df8ff69e1f4a166a127698cd5" } } ], "extra": [ 1, 6, 228, 138, 248, 175, 142, 91, 54, 192, 20, 222, 28, 48, 243, 147, 76, 144, 249, 87, 143, 36, 111, 92, 147, 21, 115, 69, 89, 200, 20, 34, 248, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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