Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3c946ebec09808431fe5f3f89c2df512050589216a993760babd5fb6b573b0b

Tx prefix hash: 0e1d8d0ca028b47bc465b30e6b39a83c13b4ad61145da2b9417ffe7c0c4752ed
Tx public key: 5eb4348ee59fef42ba71663e93869aa976b411acef9aafddc65d7acdb28e269d
Timestamp: 1729962248 Timestamp [UCT]: 2024-10-26 17:04:08 Age [y:d:h:m:s]: 00:061:21:48:57
Block: 1140119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44250 RingCT/type: yes/0
Extra: 015eb4348ee59fef42ba71663e93869aa976b411acef9aafddc65d7acdb28e269d021100000004a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0fb976b6ece2acfb0ac88c9fbe898db4b7d125e60affaa54c35dd409c19ace7 0.600000000000 1623914 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": 1140129, "vin": [ { "gen": { "height": 1140119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0fb976b6ece2acfb0ac88c9fbe898db4b7d125e60affaa54c35dd409c19ace7" } } ], "extra": [ 1, 94, 180, 52, 142, 229, 159, 239, 66, 186, 113, 102, 62, 147, 134, 154, 169, 118, 180, 17, 172, 239, 154, 175, 221, 198, 93, 122, 205, 178, 142, 38, 157, 2, 17, 0, 0, 0, 4, 161, 29, 186, 152, 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