Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0c692fc13445c3e612c28a393419018b0b8aedf5ec74ea66a2cc7e37fb41d0f

Tx prefix hash: 9094cb54d74b26c93cb4ac4835c0d8409f589139439b281660e4588566ca40ae
Tx public key: 41f5e80062d75d21c21ca975a7ed0b4ec78062d4e0c68d80c51532ace8421f60
Timestamp: 1737240780 Timestamp [UCT]: 2025-01-18 22:53:00 Age [y:d:h:m:s]: 00:337:03:20:55
Block: 1200307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238542 RingCT/type: yes/0
Extra: 0141f5e80062d75d21c21ca975a7ed0b4ec78062d4e0c68d80c51532ace8421f600211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c92855927d1c4c785471c01b69aeea5588c72634da891a7c986400b72c0e358b 0.600000000000 1686950 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": 1200317, "vin": [ { "gen": { "height": 1200307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c92855927d1c4c785471c01b69aeea5588c72634da891a7c986400b72c0e358b" } } ], "extra": [ 1, 65, 245, 232, 0, 98, 215, 93, 33, 194, 28, 169, 117, 167, 237, 11, 78, 199, 128, 98, 212, 224, 198, 141, 128, 197, 21, 50, 172, 232, 66, 31, 96, 2, 17, 0, 0, 0, 6, 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