Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fcfc852c1ca7a6a2830c620300fea54442f5112ea2d37f98d921a28af110ba3

Tx prefix hash: a4266998970d408945c8d0617e1d022d9f8a6079f92033cae089f91c6d783e32
Tx public key: 2b07841ccd6764158089eb8ec65a1d855fb3749f24cca1f82cd03f1b1f457959
Timestamp: 1735472745 Timestamp [UCT]: 2024-12-29 11:45:45 Age [y:d:h:m:s]: 00:101:14:00:10
Block: 1185696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72398 RingCT/type: yes/0
Extra: 012b07841ccd6764158089eb8ec65a1d855fb3749f24cca1f82cd03f1b1f4579590211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7417c0d2e8cf1c34e6ff611f8d26e948290d782d115d33a1717612da5da6fa08 0.600000000000 1672171 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": 1185706, "vin": [ { "gen": { "height": 1185696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7417c0d2e8cf1c34e6ff611f8d26e948290d782d115d33a1717612da5da6fa08" } } ], "extra": [ 1, 43, 7, 132, 28, 205, 103, 100, 21, 128, 137, 235, 142, 198, 90, 29, 133, 95, 179, 116, 159, 36, 204, 161, 248, 44, 208, 63, 27, 31, 69, 121, 89, 2, 17, 0, 0, 0, 6, 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