Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f85618991e7c2919a4270bf8a2f7c34e7ab88c1a40b5a2405cfa908e0b94f8ad

Tx prefix hash: ca2348e42e43a8b8683a7c3db7b4877fb645eb56c6a673aac2f09ffdb101c765
Tx public key: e442bd7e73b619a5855a4ce8ac320313c08868b20b7257061a1093f758446ef5
Timestamp: 1722403908 Timestamp [UCT]: 2024-07-31 05:31:48 Age [y:d:h:m:s]: 00:265:13:49:49
Block: 1077482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189722 RingCT/type: yes/0
Extra: 01e442bd7e73b619a5855a4ce8ac320313c08868b20b7257061a1093f758446ef502110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 493c9f8edeb95079b2640afee3e0b8d08b3a320a98a606d861d3a06a59b9e1f0 0.600000000000 1550031 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": 1077492, "vin": [ { "gen": { "height": 1077482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "493c9f8edeb95079b2640afee3e0b8d08b3a320a98a606d861d3a06a59b9e1f0" } } ], "extra": [ 1, 228, 66, 189, 126, 115, 182, 25, 165, 133, 90, 76, 232, 172, 50, 3, 19, 192, 136, 104, 178, 11, 114, 87, 6, 26, 16, 147, 247, 88, 68, 110, 245, 2, 17, 0, 0, 0, 12, 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