Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93301ce46a248f03bb3381ba2f91ac64ed99d53d8768979727d281a203375010

Tx prefix hash: ad28c3aca2f4690115ee9af461958322ffc30ccebeb23157692691041a073e3e
Tx public key: ea3041be0e4a3a6e9f0f657091f005403590e509d6ed1d8635e24f90a17d66e2
Timestamp: 1697393450 Timestamp [UCT]: 2023-10-15 18:10:50 Age [y:d:h:m:s]: 01:133:03:06:28
Block: 870340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356138 RingCT/type: yes/0
Extra: 01ea3041be0e4a3a6e9f0f657091f005403590e509d6ed1d8635e24f90a17d66e202110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.802051604000 dcy

stealth address amount amount idx
00: f2fbd97a67958837c043f8f9dee172d8bc5f81e0138d048579e2c14a76cffd38 0.802051604000 1325219 of 0

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": 870350, "vin": [ { "gen": { "height": 870340 } } ], "vout": [ { "amount": 802051604, "target": { "key": "f2fbd97a67958837c043f8f9dee172d8bc5f81e0138d048579e2c14a76cffd38" } } ], "extra": [ 1, 234, 48, 65, 190, 14, 74, 58, 110, 159, 15, 101, 112, 145, 240, 5, 64, 53, 144, 229, 9, 214, 237, 29, 134, 53, 226, 79, 144, 161, 125, 102, 226, 2, 17, 0, 0, 0, 12, 117, 227, 240, 233, 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