Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfce8b2bf9d9a18b7a6458733ccd2faed1f18dddcb563b91e5cef8419349b06c

Tx prefix hash: 6d221049574ae6b9ca10bd11d5c13a3d2c50fad6122079a2ca20f1ded482d7a0
Tx public key: 1994a5d181c5eed151b7fa7f222daace595894f1a0784838fba5d2ae359b284e
Timestamp: 1713688447 Timestamp [UCT]: 2024-04-21 08:34:07 Age [y:d:h:m:s]: 00:200:16:18:27
Block: 1005231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143663 RingCT/type: yes/0
Extra: 011994a5d181c5eed151b7fa7f222daace595894f1a0784838fba5d2ae359b284e02110000000f7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33bba2445994c2bdc3614d97b7d323469530acfc55c401a01988a9240f0895b1 0.600000000000 1465815 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": 1005241, "vin": [ { "gen": { "height": 1005231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33bba2445994c2bdc3614d97b7d323469530acfc55c401a01988a9240f0895b1" } } ], "extra": [ 1, 25, 148, 165, 209, 129, 197, 238, 209, 81, 183, 250, 127, 34, 45, 170, 206, 89, 88, 148, 241, 160, 120, 72, 56, 251, 165, 210, 174, 53, 155, 40, 78, 2, 17, 0, 0, 0, 15, 122, 156, 244, 199, 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