Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d19097b9ffb0e5003eff1d277b91f6baf5d30439a95878b952870d3fd61a772e

Tx prefix hash: 1fcdc24581a7932a2e3cb549f2427752cd3c8205832356f24421c8c64233a0b6
Tx public key: f5d7de38848c4c0d8ab52e44a276763147ee583ea68f423dabbdc867bf6032bf
Timestamp: 1745654215 Timestamp [UCT]: 2025-04-26 07:56:55 Age [y:d:h:m:s]: 00:280:12:36:22
Block: 1269729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198122 RingCT/type: yes/0
Extra: 01f5d7de38848c4c0d8ab52e44a276763147ee583ea68f423dabbdc867bf6032bf02110000000b6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11d733da802884f212f18dc3b4af06c311194932c8861a58a0fd436b59e71643 0.600000000000 1756968 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": 1269739, "vin": [ { "gen": { "height": 1269729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11d733da802884f212f18dc3b4af06c311194932c8861a58a0fd436b59e71643" } } ], "extra": [ 1, 245, 215, 222, 56, 132, 140, 76, 13, 138, 181, 46, 68, 162, 118, 118, 49, 71, 238, 88, 62, 166, 143, 66, 61, 171, 189, 200, 103, 191, 96, 50, 191, 2, 17, 0, 0, 0, 11, 108, 152, 170, 61, 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