Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4b6f26bbe5ab30b868af907921a8b75841d169a45a3f62adbc3fbfe5aafc240

Tx prefix hash: d69eb530f462b2610be307cd90e356ef7339900a917983841e4f94096bd50d0d
Tx public key: 7e5c29e8aabd539087f19b235f4147aa8a87973052b72fd27ba6ef6d37fda6e1
Timestamp: 1720390591 Timestamp [UCT]: 2024-07-07 22:16:31 Age [y:d:h:m:s]: 00:252:04:42:30
Block: 1060794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180181 RingCT/type: yes/0
Extra: 017e5c29e8aabd539087f19b235f4147aa8a87973052b72fd27ba6ef6d37fda6e1021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ac569c137e9402c05904a4f51c45fbfffdc06bd6948b8c304ab774cc13665a1 0.600000000000 1531281 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": 1060804, "vin": [ { "gen": { "height": 1060794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ac569c137e9402c05904a4f51c45fbfffdc06bd6948b8c304ab774cc13665a1" } } ], "extra": [ 1, 126, 92, 41, 232, 170, 189, 83, 144, 135, 241, 155, 35, 95, 65, 71, 170, 138, 135, 151, 48, 82, 183, 47, 210, 123, 166, 239, 109, 55, 253, 166, 225, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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