Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b03df314afb50eb1dff00733debbb9d1f9931c86ac868f24d9ba727719396e95

Tx prefix hash: 450ef65c51df8ee5199a4d8b232419b34a5141b0107c141ad953f07656a29fb5
Tx public key: 43f51cb68f57fdeeae8e942eaeb1c78ec93e851ae76766a390f9dee3c29f58b7
Timestamp: 1741848511 Timestamp [UCT]: 2025-03-13 06:48:31 Age [y:d:h:m:s]: 00:002:18:10:46
Block: 1238240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1970 RingCT/type: yes/0
Extra: 0143f51cb68f57fdeeae8e942eaeb1c78ec93e851ae76766a390f9dee3c29f58b70211000000131f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3392ae4f942a08f7c59a6764d787ad562c5e97a95935c211353227691a494671 0.600000000000 1725199 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": 1238250, "vin": [ { "gen": { "height": 1238240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3392ae4f942a08f7c59a6764d787ad562c5e97a95935c211353227691a494671" } } ], "extra": [ 1, 67, 245, 28, 182, 143, 87, 253, 238, 174, 142, 148, 46, 174, 177, 199, 142, 201, 62, 133, 26, 231, 103, 102, 163, 144, 249, 222, 227, 194, 159, 88, 183, 2, 17, 0, 0, 0, 19, 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