Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a229a562386a668e9b10cf385a3402c95c33ac09b28fee348f5f76041f1ea50e

Tx prefix hash: 369ee9653dff8dae875f3c1170c29dc726af67ff19cf5b37d530e30ded02d4f9
Tx public key: d76df5f089172e70978835c3a1c1beed9a3f62df711df8dc4764ad690b68d05d
Timestamp: 1715962482 Timestamp [UCT]: 2024-05-17 16:14:42 Age [y:d:h:m:s]: 00:167:03:07:09
Block: 1024085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119629 RingCT/type: yes/0
Extra: 01d76df5f089172e70978835c3a1c1beed9a3f62df711df8dc4764ad690b68d05d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c18b810bc08f2b94b7c82d2f934304c3921ed287772f9b8a3fd8e1da9572bfc7 0.600000000000 1489556 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": 1024095, "vin": [ { "gen": { "height": 1024085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c18b810bc08f2b94b7c82d2f934304c3921ed287772f9b8a3fd8e1da9572bfc7" } } ], "extra": [ 1, 215, 109, 245, 240, 137, 23, 46, 112, 151, 136, 53, 195, 161, 193, 190, 237, 154, 63, 98, 223, 113, 29, 248, 220, 71, 100, 173, 105, 11, 104, 208, 93, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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