Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 810dc8c7763013b9f4946c7537855ea800994cda5622ca3159098bcb01ce2328

Tx prefix hash: bbc91a0335198ade16c1ceb324771ea9f91e3c9cf14e6514e6e7366c991f81b7
Tx public key: acea8c49317c087f77ba3caf55f6638301db8ba6cc5af8caeaf5c1ab688b0d1d
Timestamp: 1725612777 Timestamp [UCT]: 2024-09-06 08:52:57 Age [y:d:h:m:s]: 00:258:15:50:03
Block: 1104091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184745 RingCT/type: yes/0
Extra: 01acea8c49317c087f77ba3caf55f6638301db8ba6cc5af8caeaf5c1ab688b0d1d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55d2a2f706d136f246eda4c83792e2d8b58e4ad9ecea353a06a44130c940f23b 0.600000000000 1581154 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": 1104101, "vin": [ { "gen": { "height": 1104091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55d2a2f706d136f246eda4c83792e2d8b58e4ad9ecea353a06a44130c940f23b" } } ], "extra": [ 1, 172, 234, 140, 73, 49, 124, 8, 127, 119, 186, 60, 175, 85, 246, 99, 131, 1, 219, 139, 166, 204, 90, 248, 202, 234, 245, 193, 171, 104, 139, 13, 29, 2, 17, 0, 0, 0, 4, 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