Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a62b34c25b4ff8a935ad0debdc3871830d75b731e041b005207a1baa2d0fb33

Tx prefix hash: b0a0bdbc6d461ee4fa04e7a6c1faefe4785a664c7600f377a82444b03eb98099
Tx public key: 441fc5c18877d99f4a3c2270efcc6703637ffd27505ad860c42ab2b1900539a8
Timestamp: 1716634791 Timestamp [UCT]: 2024-05-25 10:59:51 Age [y:d:h:m:s]: 00:318:01:52:52
Block: 1029674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227310 RingCT/type: yes/0
Extra: 01441fc5c18877d99f4a3c2270efcc6703637ffd27505ad860c42ab2b1900539a802110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04932094cf61168cdc9d0e9d7f80bfc78a42f7ff5b7ee4e7a3d0de1a4cfe1b14 0.600000000000 1497827 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": 1029684, "vin": [ { "gen": { "height": 1029674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04932094cf61168cdc9d0e9d7f80bfc78a42f7ff5b7ee4e7a3d0de1a4cfe1b14" } } ], "extra": [ 1, 68, 31, 197, 193, 136, 119, 217, 159, 74, 60, 34, 112, 239, 204, 103, 3, 99, 127, 253, 39, 80, 90, 216, 96, 196, 42, 178, 177, 144, 5, 57, 168, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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