Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 003e9c0fce5696468c0f3aec7748e37ba00af381523abc7d6c97256d037b2437

Tx prefix hash: bd0299874d5403f652903030b01a05d03ce6ff98b9a99417715f5f65aa537bfe
Tx public key: 68c4c86409ceb232ec1f70a491c278807e94aa3d181420e5ba6e13c8251df327
Timestamp: 1734223063 Timestamp [UCT]: 2024-12-15 00:37:43 Age [y:d:h:m:s]: 00:111:14:57:12
Block: 1175374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79554 RingCT/type: yes/0
Extra: 0168c4c86409ceb232ec1f70a491c278807e94aa3d181420e5ba6e13c8251df327021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3bbffee6f8cd54fe5d82caa12d9f895f8cb4dfaf4b9bd49932ee8d0192d91c7 0.600000000000 1661647 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": 1175384, "vin": [ { "gen": { "height": 1175374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3bbffee6f8cd54fe5d82caa12d9f895f8cb4dfaf4b9bd49932ee8d0192d91c7" } } ], "extra": [ 1, 104, 196, 200, 100, 9, 206, 178, 50, 236, 31, 112, 164, 145, 194, 120, 128, 126, 148, 170, 61, 24, 20, 32, 229, 186, 110, 19, 200, 37, 29, 243, 39, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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