Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 459247bb9eea9e8b94dc3dbd01b329c487e912b1567e6a58e59cc499c2e92ebe

Tx prefix hash: c29f36b101fe4f9e550756238fefeed2efe0c73f2972ae91930d365ef94c15b6
Tx public key: b36d5a57952522bdfdc07548063bacb6c79a0813a38a2675f5ba0b383cfb72fc
Timestamp: 1741836625 Timestamp [UCT]: 2025-03-13 03:30:25 Age [y:d:h:m:s]: 00:296:04:13:26
Block: 1238138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209471 RingCT/type: yes/0
Extra: 01b36d5a57952522bdfdc07548063bacb6c79a0813a38a2675f5ba0b383cfb72fc0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 911761ad2e3178e9d5e5f428d217953d2160e1b5eb1c4e4f5e9683ae24b23684 0.600000000000 1725097 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": 1238148, "vin": [ { "gen": { "height": 1238138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "911761ad2e3178e9d5e5f428d217953d2160e1b5eb1c4e4f5e9683ae24b23684" } } ], "extra": [ 1, 179, 109, 90, 87, 149, 37, 34, 189, 253, 192, 117, 72, 6, 59, 172, 182, 199, 154, 8, 19, 163, 138, 38, 117, 245, 186, 11, 56, 60, 251, 114, 252, 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