Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9498992205000ca54ccf1c5df1240a1ba848086e6a39b752a167427c11a6f3ba

Tx prefix hash: 1a95e336b89b624e0f27c9ad62c0a00e71f60b33bbc93d46a0f19ef1638b84c4
Tx public key: ad010b81fb9c5c93ba5358aa4e784ade956d35e048e8f588ddc4a11f4c45f1b5
Timestamp: 1736838482 Timestamp [UCT]: 2025-01-14 07:08:02 Age [y:d:h:m:s]: 00:155:05:17:35
Block: 1197006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110651 RingCT/type: yes/0
Extra: 01ad010b81fb9c5c93ba5358aa4e784ade956d35e048e8f588ddc4a11f4c45f1b50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fc342c1b33e0b466a44b38654e4d7bf65a2a6d29e2ed602dc6e54a04d9f4fea 0.600000000000 1683611 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": 1197016, "vin": [ { "gen": { "height": 1197006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fc342c1b33e0b466a44b38654e4d7bf65a2a6d29e2ed602dc6e54a04d9f4fea" } } ], "extra": [ 1, 173, 1, 11, 129, 251, 156, 92, 147, 186, 83, 88, 170, 78, 120, 74, 222, 149, 109, 53, 224, 72, 232, 245, 136, 221, 196, 161, 31, 76, 69, 241, 181, 2, 17, 0, 0, 0, 2, 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