Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35d0fca60939f5093cb7f20f2975bdf87b89d9e9ea2e06f4a78f78e89a394663

Tx prefix hash: ac786001e6e4e41334398e48b6587840754283490d7d38d1512a0d468a7baf4f
Tx public key: c8f9b35d8111d34c38e838b2bade44efa6ceaf3ee6492415457b048f2c0847f6
Timestamp: 1716183731 Timestamp [UCT]: 2024-05-20 05:42:11 Age [y:d:h:m:s]: 00:346:11:11:05
Block: 1025920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247645 RingCT/type: yes/0
Extra: 01c8f9b35d8111d34c38e838b2bade44efa6ceaf3ee6492415457b048f2c0847f602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91065d3c913ca77f4148781a7c1c6ab5d7ea6104d486013c83c77eb09204e49c 0.600000000000 1492719 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": 1025930, "vin": [ { "gen": { "height": 1025920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91065d3c913ca77f4148781a7c1c6ab5d7ea6104d486013c83c77eb09204e49c" } } ], "extra": [ 1, 200, 249, 179, 93, 129, 17, 211, 76, 56, 232, 56, 178, 186, 222, 68, 239, 166, 206, 175, 62, 230, 73, 36, 21, 69, 123, 4, 143, 44, 8, 71, 246, 2, 17, 0, 0, 0, 3, 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