Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e09b4452d3d42c6e557704ab4cc61808a7f11afb73ae13898eb3cbe660f4a6c3

Tx prefix hash: fbb3046462154b39e6da3bab3a58cebb2e448a4a19532bafa37e507a411bbee0
Tx public key: 79d095a1abd627c481b05ce7e336e82e0dfef84f283064895bb45190c5ac509f
Timestamp: 1715941136 Timestamp [UCT]: 2024-05-17 10:18:56 Age [y:d:h:m:s]: 00:236:08:50:44
Block: 1023906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169169 RingCT/type: yes/0
Extra: 0179d095a1abd627c481b05ce7e336e82e0dfef84f283064895bb45190c5ac509f02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 210305bae23d52ad0b9c9cd04ea622a5b21b29db1b75a924266d6c41ca08e963 0.600000000000 1489237 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": 1023916, "vin": [ { "gen": { "height": 1023906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "210305bae23d52ad0b9c9cd04ea622a5b21b29db1b75a924266d6c41ca08e963" } } ], "extra": [ 1, 121, 208, 149, 161, 171, 214, 39, 196, 129, 176, 92, 231, 227, 54, 232, 46, 13, 254, 248, 79, 40, 48, 100, 137, 91, 180, 81, 144, 197, 172, 80, 159, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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