Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 471407308d44ba1308e2171fb4949eab74ef9a76108aef6f80bb95814ed3a062

Tx prefix hash: 8d164c4c09c4dc0f76e6c2e3b912279d10b67320b5b053134be27e6432b11a10
Tx public key: 102309c7ae65f46c17ec3eb97467d9eff4befd51ed5999343d07f06fccc807f6
Timestamp: 1721879941 Timestamp [UCT]: 2024-07-25 03:59:01 Age [y:d:h:m:s]: 00:265:18:08:02
Block: 1073136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189860 RingCT/type: yes/0
Extra: 01102309c7ae65f46c17ec3eb97467d9eff4befd51ed5999343d07f06fccc807f602110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4cd234f6b0ebcaef65c1db9c76075091bece56e7ffb530827b0bb7b40ceeadc 0.600000000000 1545635 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": 1073146, "vin": [ { "gen": { "height": 1073136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4cd234f6b0ebcaef65c1db9c76075091bece56e7ffb530827b0bb7b40ceeadc" } } ], "extra": [ 1, 16, 35, 9, 199, 174, 101, 244, 108, 23, 236, 62, 185, 116, 103, 217, 239, 244, 190, 253, 81, 237, 89, 153, 52, 61, 7, 240, 111, 204, 200, 7, 246, 2, 17, 0, 0, 0, 14, 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