Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f75a3199f49ff8120cfbc230d2a33095bc6e4405bf522578677f29edbc15dd1c

Tx prefix hash: c12d89fbc929acebe57cf11a952fd854dc7445f5155d93a4d0732a55e6999df1
Tx public key: c123ac1f41f8f4ecc4b52f85968054aa04a10c648d7b814ae047256240e235e9
Timestamp: 1696235857 Timestamp [UCT]: 2023-10-02 08:37:37 Age [y:d:h:m:s]: 01:198:15:59:05
Block: 860738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403034 RingCT/type: yes/0
Extra: 01c123ac1f41f8f4ecc4b52f85968054aa04a10c648d7b814ae047256240e235e902110000000175e3f0e9000000000000000000

1 output(s) for total of 0.863013794000 dcy

stealth address amount amount idx
00: 54df5a91e6b65588813de79633e1d12d9c35d903775198f75b60d6fb61c45b66 0.863013794000 1315036 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": 860748, "vin": [ { "gen": { "height": 860738 } } ], "vout": [ { "amount": 863013794, "target": { "key": "54df5a91e6b65588813de79633e1d12d9c35d903775198f75b60d6fb61c45b66" } } ], "extra": [ 1, 193, 35, 172, 31, 65, 248, 244, 236, 196, 181, 47, 133, 150, 128, 84, 170, 4, 161, 12, 100, 141, 123, 129, 74, 224, 71, 37, 98, 64, 226, 53, 233, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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