Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 358ca15c61bc1876c842fe5ab667d88fcef2c638a3b09d203804ed93f97d9a56

Tx prefix hash: 509d76ffb5af0614891e248e2a4d46c1dea4f45fa8a559b34783addf05539d9e
Tx public key: 69aee06a28a38e50c0a518abd3d6e3e85057c801f57ab2ebc4033c43c3430959
Timestamp: 1716113303 Timestamp [UCT]: 2024-05-19 10:08:23 Age [y:d:h:m:s]: 00:262:07:37:20
Block: 1025343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187457 RingCT/type: yes/0
Extra: 0169aee06a28a38e50c0a518abd3d6e3e85057c801f57ab2ebc4033c43c34309590211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 894cb08c95fec14ee0ccae4fc25db0402aaaec85350f5b216a0870ca851b10c7 0.600000000000 1491776 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": 1025353, "vin": [ { "gen": { "height": 1025343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "894cb08c95fec14ee0ccae4fc25db0402aaaec85350f5b216a0870ca851b10c7" } } ], "extra": [ 1, 105, 174, 224, 106, 40, 163, 142, 80, 192, 165, 24, 171, 211, 214, 227, 232, 80, 87, 200, 1, 245, 122, 178, 235, 196, 3, 60, 67, 195, 67, 9, 89, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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