Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a16501d5450a8e5888b39b83982cb86e55f03f3f1c67cf105495b6f3424aaefe

Tx prefix hash: 9fcf6abc26ab733f1884def8ea8e76fe9e2d1f610090f65f4bc4ae030c274f6b
Tx public key: 99de6e3fdd3d6d3365eab9de1dfa92981dec254ffe63acd94c1dd6191497c043
Timestamp: 1735449169 Timestamp [UCT]: 2024-12-29 05:12:49 Age [y:d:h:m:s]: 00:078:07:20:40
Block: 1185502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55769 RingCT/type: yes/0
Extra: 0199de6e3fdd3d6d3365eab9de1dfa92981dec254ffe63acd94c1dd6191497c0430211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 262c3f04337031076bc58acff0d832935266598b7a72279e53e107ab6b2560b7 0.600000000000 1671975 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": 1185512, "vin": [ { "gen": { "height": 1185502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "262c3f04337031076bc58acff0d832935266598b7a72279e53e107ab6b2560b7" } } ], "extra": [ 1, 153, 222, 110, 63, 221, 61, 109, 51, 101, 234, 185, 222, 29, 250, 146, 152, 29, 236, 37, 79, 254, 99, 172, 217, 76, 29, 214, 25, 20, 151, 192, 67, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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