Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d0e67050bdc188e7d6f5502212bbd76c4a3dd8b0da07c5e97bf0bea023db9a

Tx prefix hash: 8a6f706a5df5c1658f73f6da297a74f3ffcd6641460c239ecfb7965f10535316
Tx public key: c23d4ec58aa78bf48900e35a8bc235fbd5e9a78c503024bb82aad1fffbd86fb3
Timestamp: 1754697304 Timestamp [UCT]: 2025-08-08 23:55:04 Age [y:d:h:m:s]: 00:097:16:50:49
Block: 1343129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68940 RingCT/type: yes/0
Extra: 01c23d4ec58aa78bf48900e35a8bc235fbd5e9a78c503024bb82aad1fffbd86fb3021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1278c266dc2dddeaa6561f0ec0875915539e5c6267968761e805ada98bc6beb1 0.600000000000 1830964 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": 1343139, "vin": [ { "gen": { "height": 1343129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1278c266dc2dddeaa6561f0ec0875915539e5c6267968761e805ada98bc6beb1" } } ], "extra": [ 1, 194, 61, 78, 197, 138, 167, 139, 244, 137, 0, 227, 90, 139, 194, 53, 251, 213, 233, 167, 140, 80, 48, 36, 187, 130, 170, 209, 255, 251, 216, 111, 179, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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