Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 167e020729b463ebbf8ea4e400a65a380ea30dfc354cd1cf8284ad516c74506f

Tx prefix hash: bf9e86f8a333bf1a6160fb399f69807301ea3821549a90f8d8cbd327cd3b67cf
Tx public key: d906084fd44ed3ec053bb369646ae017ad9b4cf7e02ab120b970f80f2c17a8c3
Timestamp: 1725935067 Timestamp [UCT]: 2024-09-10 02:24:27 Age [y:d:h:m:s]: 00:127:05:31:42
Block: 1106768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90978 RingCT/type: yes/0
Extra: 01d906084fd44ed3ec053bb369646ae017ad9b4cf7e02ab120b970f80f2c17a8c302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af0b659aeeb9142749b08510be20a3c443f2dfb86f41d4267de0cb5d3a820b3e 0.600000000000 1584369 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": 1106778, "vin": [ { "gen": { "height": 1106768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af0b659aeeb9142749b08510be20a3c443f2dfb86f41d4267de0cb5d3a820b3e" } } ], "extra": [ 1, 217, 6, 8, 79, 212, 78, 211, 236, 5, 59, 179, 105, 100, 106, 224, 23, 173, 155, 76, 247, 224, 42, 177, 32, 185, 112, 248, 15, 44, 23, 168, 195, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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