Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 507324ca0d446ae5a5e0224eb58f6c0d3109d2dd9f723b9327b5910d3c107253

Tx prefix hash: 1422e09405beb9667d1a0cc91096fa6207732a8f5d334ea2be545fd94475b396
Tx public key: 3e18f3c18a04ade8f99fed1d0cda6de3a55dd9e7014748f25ef19398ba8586f9
Timestamp: 1713753947 Timestamp [UCT]: 2024-04-22 02:45:47 Age [y:d:h:m:s]: 01:056:15:37:32
Block: 1005762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301352 RingCT/type: yes/0
Extra: 013e18f3c18a04ade8f99fed1d0cda6de3a55dd9e7014748f25ef19398ba8586f90211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79838892d60248379f16a1b559231c751aae1dc8746001fafab641dd5bfcaac8 0.600000000000 1466558 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": 1005772, "vin": [ { "gen": { "height": 1005762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79838892d60248379f16a1b559231c751aae1dc8746001fafab641dd5bfcaac8" } } ], "extra": [ 1, 62, 24, 243, 193, 138, 4, 173, 232, 249, 159, 237, 29, 12, 218, 109, 227, 165, 93, 217, 231, 1, 71, 72, 242, 94, 241, 147, 152, 186, 133, 134, 249, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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