Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94f87a4d3ae6625c04510aeb6176c438d6db06b1a461bda9c1f01a10cafb5db3

Tx prefix hash: cfc912d1b65ec92174d8c99a9252f4e644e787286172acff4cb9b1cbd60cacde
Tx public key: 3d5436ac7f8af284f8331f743e6c43acdba4af00e2ff01a24d1fec9713281389
Timestamp: 1713504327 Timestamp [UCT]: 2024-04-19 05:25:27 Age [y:d:h:m:s]: 01:196:14:27:19
Block: 1003700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399161 RingCT/type: yes/0
Extra: 013d5436ac7f8af284f8331f743e6c43acdba4af00e2ff01a24d1fec9713281389021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 803a86494f1ad86d0a15763e2c035f8d88481461ccae99fdf5139340bad181b4 0.600000000000 1464242 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": 1003710, "vin": [ { "gen": { "height": 1003700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "803a86494f1ad86d0a15763e2c035f8d88481461ccae99fdf5139340bad181b4" } } ], "extra": [ 1, 61, 84, 54, 172, 127, 138, 242, 132, 248, 51, 31, 116, 62, 108, 67, 172, 219, 164, 175, 0, 226, 255, 1, 162, 77, 31, 236, 151, 19, 40, 19, 137, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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