Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84d4b3165dd3d06eaf07ae6230d92b7b72c0323824d4fb660cb92118f671b607

Tx prefix hash: 0ef518d9acdb8081540a0f4b89ba2092df2ac80fc8aae2e44ce965091ca274fa
Tx public key: 9b9d5de77863e9e6ebd49ccae2692696f5c0e283b93fba1ba6ba1e99c9a38b90
Timestamp: 1736668456 Timestamp [UCT]: 2025-01-12 07:54:16 Age [y:d:h:m:s]: 00:095:01:21:36
Block: 1195600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67726 RingCT/type: yes/0
Extra: 019b9d5de77863e9e6ebd49ccae2692696f5c0e283b93fba1ba6ba1e99c9a38b900211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 455e69d63f8f7d874c2007902420e91406b2a7e2490496fc621a93f3e6f3f6b7 0.600000000000 1682191 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": 1195610, "vin": [ { "gen": { "height": 1195600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "455e69d63f8f7d874c2007902420e91406b2a7e2490496fc621a93f3e6f3f6b7" } } ], "extra": [ 1, 155, 157, 93, 231, 120, 99, 233, 230, 235, 212, 156, 202, 226, 105, 38, 150, 245, 192, 226, 131, 185, 63, 186, 27, 166, 186, 30, 153, 201, 163, 139, 144, 2, 17, 0, 0, 0, 9, 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