Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c20d4506f40c395b6d48f5767ee0dae0c03a6d63fc516fe9bd409cf7054c7783

Tx prefix hash: a8aa9e01f51fd46fa605dc34bbfdef54bd41351536bab8e5a4b736afda37e5af
Tx public key: 3aed8df20262561863fee8fdd1a0119ae0b052e4361c4358523716fbc96e9a85
Timestamp: 1723891814 Timestamp [UCT]: 2024-08-17 10:50:14 Age [y:d:h:m:s]: 00:209:13:55:13
Block: 1089832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149655 RingCT/type: yes/0
Extra: 013aed8df20262561863fee8fdd1a0119ae0b052e4361c4358523716fbc96e9a8502110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0550cff6de69b85d7a9e1f9693781604d1c8c003bcb77f25ab5e29b3a525a931 0.600000000000 1564455 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": 1089842, "vin": [ { "gen": { "height": 1089832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0550cff6de69b85d7a9e1f9693781604d1c8c003bcb77f25ab5e29b3a525a931" } } ], "extra": [ 1, 58, 237, 141, 242, 2, 98, 86, 24, 99, 254, 232, 253, 209, 160, 17, 154, 224, 176, 82, 228, 54, 28, 67, 88, 82, 55, 22, 251, 201, 110, 154, 133, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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