Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26e4c107ea2b74ca618ff70f3dd1cf1ac8252da39224d2924c49b16209bf2d3f

Tx prefix hash: 9947163c3c577209786eec085a3b74f22699b3d35109207bcf8f15a5ecf0e590
Tx public key: f50c7c1f4370696cb274e60e6c87faccce22179fd7abc4532a2333aa4743be21
Timestamp: 1702526583 Timestamp [UCT]: 2023-12-14 04:03:03 Age [y:d:h:m:s]: 01:163:14:54:15
Block: 912691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378114 RingCT/type: yes/0
Extra: 01f50c7c1f4370696cb274e60e6c87faccce22179fd7abc4532a2333aa4743be2102110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e10d3b5d2a62d28bff90c5c502d6561b2674915d93ad17a6a726ec0cdc600930 0.600000000000 1369925 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": 912701, "vin": [ { "gen": { "height": 912691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e10d3b5d2a62d28bff90c5c502d6561b2674915d93ad17a6a726ec0cdc600930" } } ], "extra": [ 1, 245, 12, 124, 31, 67, 112, 105, 108, 178, 116, 230, 14, 108, 135, 250, 204, 206, 34, 23, 159, 215, 171, 196, 83, 42, 35, 51, 170, 71, 67, 190, 33, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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