Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6efed485eb23e3bbf6d4bd1b85b9f8e7ba2d6b64fb43f6b059be68c60c31e7f9

Tx prefix hash: a793adcbb698f282b7dd2b9e8b70d47c50a0e3f24bf2431ecf4a4176cb012630
Tx public key: 77b36c0ee6726d0ad27c59b5f0d0556199fb01908a8295217cb2ee7044e98e7b
Timestamp: 1725699487 Timestamp [UCT]: 2024-09-07 08:58:07 Age [y:d:h:m:s]: 00:242:14:19:23
Block: 1104811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173242 RingCT/type: yes/0
Extra: 0177b36c0ee6726d0ad27c59b5f0d0556199fb01908a8295217cb2ee7044e98e7b021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62e4466f31fcb25f2e0619db5f84690bd7ddd8d6a818be6662ed45d1bfbb9af2 0.600000000000 1582094 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": 1104821, "vin": [ { "gen": { "height": 1104811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62e4466f31fcb25f2e0619db5f84690bd7ddd8d6a818be6662ed45d1bfbb9af2" } } ], "extra": [ 1, 119, 179, 108, 14, 230, 114, 109, 10, 210, 124, 89, 181, 240, 208, 85, 97, 153, 251, 1, 144, 138, 130, 149, 33, 124, 178, 238, 112, 68, 233, 142, 123, 2, 17, 0, 0, 0, 3, 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