Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bde1da2beb077e545601c404f17c1c263c54920f5f04e8ac7d9263e865d84b6

Tx prefix hash: 3075633da45abc8f4b2e9dafc06b23eac0117710dab7df402ebbbbcf81fbf47d
Tx public key: c4e226a07596d91da7c178cbbe017064fe30edbbdb8e719b571d814aa8793b17
Timestamp: 1725201332 Timestamp [UCT]: 2024-09-01 14:35:32 Age [y:d:h:m:s]: 00:229:05:38:27
Block: 1100682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163696 RingCT/type: yes/0
Extra: 01c4e226a07596d91da7c178cbbe017064fe30edbbdb8e719b571d814aa8793b17021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a200c9b2da259c99c83ea96c68523cf04243c7b4f043d0e87048ae1164f23d0c 0.600000000000 1576661 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": 1100692, "vin": [ { "gen": { "height": 1100682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a200c9b2da259c99c83ea96c68523cf04243c7b4f043d0e87048ae1164f23d0c" } } ], "extra": [ 1, 196, 226, 38, 160, 117, 150, 217, 29, 167, 193, 120, 203, 190, 1, 112, 100, 254, 48, 237, 187, 219, 142, 113, 155, 87, 29, 129, 74, 168, 121, 59, 23, 2, 17, 0, 0, 0, 9, 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