Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db6932c4c4ef01dad168ac8f3b4422742b7548bb44a3f9f3815c514b715f9cde

Tx prefix hash: 4245f7b46ab8caeaca6d60658cd9fcb8f6cbebfe792244bd1ca09ceaa12240bc
Tx public key: cc3ae89237b417cda954e2b78eba49007a4f8e536f3e101e486dec662ed093a6
Timestamp: 1750215733 Timestamp [UCT]: 2025-06-18 03:02:13 Age [y:d:h:m:s]: 00:194:13:35:45
Block: 1307377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136916 RingCT/type: yes/0
Extra: 01cc3ae89237b417cda954e2b78eba49007a4f8e536f3e101e486dec662ed093a602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d17cc6a4f3d166f07f262eba020ba1009b9bf96cb1ca772fc1ff8b66ebec5fd7 0.600000000000 1794988 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": 1307387, "vin": [ { "gen": { "height": 1307377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d17cc6a4f3d166f07f262eba020ba1009b9bf96cb1ca772fc1ff8b66ebec5fd7" } } ], "extra": [ 1, 204, 58, 232, 146, 55, 180, 23, 205, 169, 84, 226, 183, 142, 186, 73, 0, 122, 79, 142, 83, 111, 62, 16, 30, 72, 109, 236, 102, 46, 208, 147, 166, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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