Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2755ba14846c8ba07d9bc38f3ff0450845f0078637ac0505e18cd73dc3c5f71

Tx prefix hash: 536fa5f0110406d1962d142397f6bcab98c25e6eae6aba084c47a3a907da6411
Tx public key: bbadfca9caa7bdbc074e1e34779d35175d6d4cf8f8b6de81fc645e18b4ccd107
Timestamp: 1738256666 Timestamp [UCT]: 2025-01-30 17:04:26 Age [y:d:h:m:s]: 00:338:20:22:37
Block: 1208489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240018 RingCT/type: yes/0
Extra: 01bbadfca9caa7bdbc074e1e34779d35175d6d4cf8f8b6de81fc645e18b4ccd1070211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bba465a8990a496d1c1c5a1c9aaed214c7b550adddc9a4ad7a3158741049ccc6 0.600000000000 1695222 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": 1208499, "vin": [ { "gen": { "height": 1208489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bba465a8990a496d1c1c5a1c9aaed214c7b550adddc9a4ad7a3158741049ccc6" } } ], "extra": [ 1, 187, 173, 252, 169, 202, 167, 189, 188, 7, 78, 30, 52, 119, 157, 53, 23, 93, 109, 76, 248, 248, 182, 222, 129, 252, 100, 94, 24, 180, 204, 209, 7, 2, 17, 0, 0, 0, 9, 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