Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df510e4401b14fbcc86ede6d35fd523cbf6444a39b392be3c3ffa8174f0ea41a

Tx prefix hash: 68fba920853d4b24a821cfad5034162d659099c322994dd58745bec93b2d370b
Tx public key: 3500e3a3a647e4237f87f514363b40e97b7a25b4ed6d2bb27438b31aa3f3712b
Timestamp: 1730989522 Timestamp [UCT]: 2024-11-07 14:25:22 Age [y:d:h:m:s]: 00:190:17:36:31
Block: 1148578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136172 RingCT/type: yes/0
Extra: 013500e3a3a647e4237f87f514363b40e97b7a25b4ed6d2bb27438b31aa3f3712b0211000000048368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aec52f05c10d995c8c045184de7b75da215ef602c0df00e7ca97c2508b9489a7 0.600000000000 1633459 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": 1148588, "vin": [ { "gen": { "height": 1148578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aec52f05c10d995c8c045184de7b75da215ef602c0df00e7ca97c2508b9489a7" } } ], "extra": [ 1, 53, 0, 227, 163, 166, 71, 228, 35, 127, 135, 245, 20, 54, 59, 64, 233, 123, 122, 37, 180, 237, 109, 43, 178, 116, 56, 179, 26, 163, 243, 113, 43, 2, 17, 0, 0, 0, 4, 131, 104, 38, 109, 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