Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b6b7e24bb5a1521e4f0fd488c823a996ba767fcc383c1d8d65207d4be6fa6c5

Tx prefix hash: 4554e08362160e432ac76682c5158ff33846cb93c7f48f474438a52fd15769c1
Tx public key: 77e2d669d1a98ea3d491346823d759498281e5b58507c83b4a049ba49e3518fd
Timestamp: 1727126083 Timestamp [UCT]: 2024-09-23 21:14:43 Age [y:d:h:m:s]: 01:046:15:00:23
Block: 1116636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291721 RingCT/type: yes/0
Extra: 0177e2d669d1a98ea3d491346823d759498281e5b58507c83b4a049ba49e3518fd021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c67e2d192e7c1085badd4041b8785888d57769cb69e41d77a7d84d17b80710be 0.600000000000 1597189 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": 1116646, "vin": [ { "gen": { "height": 1116636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c67e2d192e7c1085badd4041b8785888d57769cb69e41d77a7d84d17b80710be" } } ], "extra": [ 1, 119, 226, 214, 105, 209, 169, 142, 163, 212, 145, 52, 104, 35, 215, 89, 73, 130, 129, 229, 181, 133, 7, 200, 59, 74, 4, 155, 164, 158, 53, 24, 253, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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