Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2caf71d4b73a3a489689a32001edf136a519201dc6d90c7b2f8634e9b9bbd12e

Tx prefix hash: 7ec536f748538c311cdf683493f0a6bfaa9ff1ca31dc7e234eede8f16424b07e
Tx public key: f5be869eb0ce13dc43facf0022cb34081adbd34e585c01c5358d74dce38cad29
Timestamp: 1736518447 Timestamp [UCT]: 2025-01-10 14:14:07 Age [y:d:h:m:s]: 00:075:00:15:59
Block: 1194358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53377 RingCT/type: yes/0
Extra: 01f5be869eb0ce13dc43facf0022cb34081adbd34e585c01c5358d74dce38cad290211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24cb6995c0f2de5e8352ed7f8d9d71e0f78ea4d6d0d6fbb077ebe217eb7cde33 0.600000000000 1680927 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": 1194368, "vin": [ { "gen": { "height": 1194358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24cb6995c0f2de5e8352ed7f8d9d71e0f78ea4d6d0d6fbb077ebe217eb7cde33" } } ], "extra": [ 1, 245, 190, 134, 158, 176, 206, 19, 220, 67, 250, 207, 0, 34, 203, 52, 8, 26, 219, 211, 78, 88, 92, 1, 197, 53, 141, 116, 220, 227, 140, 173, 41, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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