Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc656710ef5e7726126b1bb4b8ae1f3e32c1956bbbd7133ac059c1e4a95ee0ed

Tx prefix hash: c25406e1bdf2e3964dd950d3b7ec357f924602061c0ec8f4db7266e901d134c3
Tx public key: 3b65a6067fbd98c477630b3c30e9e2216e9d22d53348f83b3f9128369802f7db
Timestamp: 1722400595 Timestamp [UCT]: 2024-07-31 04:36:35 Age [y:d:h:m:s]: 00:163:11:42:24
Block: 1077461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116955 RingCT/type: yes/0
Extra: 013b65a6067fbd98c477630b3c30e9e2216e9d22d53348f83b3f9128369802f7db02110000000194f0f54f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05c5273db8f756a45e6fa2fd3e9548842ccc8cb76955606810cca2762435d505 0.600000000000 1550008 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": 1077471, "vin": [ { "gen": { "height": 1077461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05c5273db8f756a45e6fa2fd3e9548842ccc8cb76955606810cca2762435d505" } } ], "extra": [ 1, 59, 101, 166, 6, 127, 189, 152, 196, 119, 99, 11, 60, 48, 233, 226, 33, 110, 157, 34, 213, 51, 72, 248, 59, 63, 145, 40, 54, 152, 2, 247, 219, 2, 17, 0, 0, 0, 1, 148, 240, 245, 79, 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