Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78d29d3fae66fe3acbc5fc8968a81ad5f9badf503bb3dec01eb1cfe0286d9f8d

Tx prefix hash: 2f352dd200dfff07d265b6d5b3946c488ac8f3b2f6c9a09b8cb6fc005a0012ab
Tx public key: 88f36ecb80e9a480d7d01f4db66c85f6b0e0d9b8f67b3d4d7ac2337933d941c5
Timestamp: 1728374017 Timestamp [UCT]: 2024-10-08 07:53:37 Age [y:d:h:m:s]: 00:186:17:15:56
Block: 1126982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133235 RingCT/type: yes/0
Extra: 0188f36ecb80e9a480d7d01f4db66c85f6b0e0d9b8f67b3d4d7ac2337933d941c5021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19fb386ca43d7c1fca8638dfd4305de73298a8757f172f8bb55cf404482a1c0b 0.600000000000 1609781 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": 1126992, "vin": [ { "gen": { "height": 1126982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19fb386ca43d7c1fca8638dfd4305de73298a8757f172f8bb55cf404482a1c0b" } } ], "extra": [ 1, 136, 243, 110, 203, 128, 233, 164, 128, 215, 208, 31, 77, 182, 108, 133, 246, 176, 224, 217, 184, 246, 123, 61, 77, 122, 194, 51, 121, 51, 217, 65, 197, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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