Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c18b05facc9f8b9bc390f544d4886cc8d616f8b64128c826903118796581af44

Tx prefix hash: a7a501d41b874dcbf936a89af4d792de62ef5bd87fbffb5de25a2992aec1fe91
Tx public key: 926e474246814b72b3f6f9934dfd715f4190499a2eec5f683fffe09c8731027b
Timestamp: 1723867134 Timestamp [UCT]: 2024-08-17 03:58:54 Age [y:d:h:m:s]: 00:302:03:27:03
Block: 1089622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215767 RingCT/type: yes/0
Extra: 01926e474246814b72b3f6f9934dfd715f4190499a2eec5f683fffe09c8731027b021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 495128289c2507c7447594852be4a461fd951c7c7e74b3cbc4cb1e3cc1147c8e 0.600000000000 1564245 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": 1089632, "vin": [ { "gen": { "height": 1089622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "495128289c2507c7447594852be4a461fd951c7c7e74b3cbc4cb1e3cc1147c8e" } } ], "extra": [ 1, 146, 110, 71, 66, 70, 129, 75, 114, 179, 246, 249, 147, 77, 253, 113, 95, 65, 144, 73, 154, 46, 236, 95, 104, 63, 255, 224, 156, 135, 49, 2, 123, 2, 17, 0, 0, 0, 6, 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