Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 191cf9ca9f9192200674ef8c2e5aec940208347a0eb50a5fb5636827027a52c1

Tx prefix hash: 8691cf99bc804f4e7acafa915a7a6d8d5236a5a5e0c88c308b37cb0268a85ebf
Tx public key: e404c902c4f59617088de8d134f69c97552021d7403754e83937ff1cc9d4ef3f
Timestamp: 1738431307 Timestamp [UCT]: 2025-02-01 17:35:07 Age [y:d:h:m:s]: 00:289:11:45:25
Block: 1209931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204659 RingCT/type: yes/0
Extra: 01e404c902c4f59617088de8d134f69c97552021d7403754e83937ff1cc9d4ef3f0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfd8518c8cf45e1484e1cd341781e33d40ed489f9b28e59bd79616f5c7b11bb0 0.600000000000 1696678 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": 1209941, "vin": [ { "gen": { "height": 1209931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfd8518c8cf45e1484e1cd341781e33d40ed489f9b28e59bd79616f5c7b11bb0" } } ], "extra": [ 1, 228, 4, 201, 2, 196, 245, 150, 23, 8, 141, 232, 209, 52, 246, 156, 151, 85, 32, 33, 215, 64, 55, 84, 232, 57, 55, 255, 28, 201, 212, 239, 63, 2, 17, 0, 0, 0, 4, 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