Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3989ccbea57b47927dcd3c3068cd3b99e9cc0bc7f211585c14d630d1a206aff

Tx prefix hash: 044649250eae9131d28ef15bc099ca927fa8f38a06ed04c598a6765594762e6a
Tx public key: 2dd6fb742392d5e3b5e456017f4129d13f6b012e76737cd3a61909517b1e3e68
Timestamp: 1702720906 Timestamp [UCT]: 2023-12-16 10:01:46 Age [y:d:h:m:s]: 01:115:22:27:05
Block: 914303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343991 RingCT/type: yes/0
Extra: 012dd6fb742392d5e3b5e456017f4129d13f6b012e76737cd3a61909517b1e3e6802110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 748decb8a638a002a37bf9a49a76b37ff0663ba35552b9f555cb867b74e648cd 0.600000000000 1371601 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": 914313, "vin": [ { "gen": { "height": 914303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "748decb8a638a002a37bf9a49a76b37ff0663ba35552b9f555cb867b74e648cd" } } ], "extra": [ 1, 45, 214, 251, 116, 35, 146, 213, 227, 181, 228, 86, 1, 127, 65, 41, 209, 63, 107, 1, 46, 118, 115, 124, 211, 166, 25, 9, 81, 123, 30, 62, 104, 2, 17, 0, 0, 0, 4, 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