Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30484cd4c6e7f08a0205189dd3ec85738da54ff03eb2d6e2086634a066f367c4

Tx prefix hash: 720a8678b08fc62cc7294071fe37a1dc51df8d9a588f242ff0556ec7714512fc
Tx public key: a6a4b43ad8c0cf2267fb581fded87ee961c8c309112f36e8e4cfeeabb27f30f8
Timestamp: 1759226157 Timestamp [UCT]: 2025-09-30 09:55:57 Age [y:d:h:m:s]: 00:040:14:30:38
Block: 1379638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29082 RingCT/type: yes/0
Extra: 01a6a4b43ad8c0cf2267fb581fded87ee961c8c309112f36e8e4cfeeabb27f30f8021100000005d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3c6616f52ef449219cc7f57d0e946cfa71ac1fa5c33c83e4a9aad25bbae3461 0.600000000000 1867745 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": 1379648, "vin": [ { "gen": { "height": 1379638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3c6616f52ef449219cc7f57d0e946cfa71ac1fa5c33c83e4a9aad25bbae3461" } } ], "extra": [ 1, 166, 164, 180, 58, 216, 192, 207, 34, 103, 251, 88, 31, 222, 216, 126, 233, 97, 200, 195, 9, 17, 47, 54, 232, 228, 207, 238, 171, 178, 127, 48, 248, 2, 17, 0, 0, 0, 5, 216, 231, 210, 65, 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