Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42f28b6b83779d509093a7ec7bb253bb7db93b868920a76862a2ae306286b79f

Tx prefix hash: 15d450e35f04693327de1bb1e030ebe2edba61ab0fc5328416965980f50152f5
Tx public key: 519f8e3ffc6cc21931d3fe8b2cc812e7535823aef3434c4a42e596c204652e60
Timestamp: 1720205328 Timestamp [UCT]: 2024-07-05 18:48:48 Age [y:d:h:m:s]: 01:150:18:08:13
Block: 1059250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366329 RingCT/type: yes/0
Extra: 01519f8e3ffc6cc21931d3fe8b2cc812e7535823aef3434c4a42e596c204652e600211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 105d72457c8a5bb76db2b1a858e3e50ab4c93678ea7c4b7bd384f37e824beaf4 0.600000000000 1529717 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": 1059260, "vin": [ { "gen": { "height": 1059250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "105d72457c8a5bb76db2b1a858e3e50ab4c93678ea7c4b7bd384f37e824beaf4" } } ], "extra": [ 1, 81, 159, 142, 63, 252, 108, 194, 25, 49, 211, 254, 139, 44, 200, 18, 231, 83, 88, 35, 174, 243, 67, 76, 74, 66, 229, 150, 194, 4, 101, 46, 96, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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