Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eadd633563bbe682406fd1c7c1413099aa8765a5c14f94de996b542de489e9c7

Tx prefix hash: 3e1b9f7a4561821217593375d97e7b1f51e6d44e61afc21a9e86a31f719dcfd1
Tx public key: 6641bbfbb252f98d5a20668ff038065fc6a828d959ea721c4893d224d1d53264
Timestamp: 1748997508 Timestamp [UCT]: 2025-06-04 00:38:28 Age [y:d:h:m:s]: 00:204:13:01:07
Block: 1297418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143910 RingCT/type: yes/0
Extra: 016641bbfbb252f98d5a20668ff038065fc6a828d959ea721c4893d224d1d53264021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 264a34aeadb877b8bbbe9370a9f6082cde2124e4f95890bd4f0a1e95b960c938 0.600000000000 1784937 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": 1297428, "vin": [ { "gen": { "height": 1297418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "264a34aeadb877b8bbbe9370a9f6082cde2124e4f95890bd4f0a1e95b960c938" } } ], "extra": [ 1, 102, 65, 187, 251, 178, 82, 249, 141, 90, 32, 102, 143, 240, 56, 6, 95, 198, 168, 40, 217, 89, 234, 114, 28, 72, 147, 210, 36, 209, 213, 50, 100, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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