Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33bf35f3a8de6911e22bc2b671f73a2e0abc5e92853aa15dfd10f30224769c80

Tx prefix hash: 7ae8f8deea1af67f049e9b18f8b3a72e2b38b58c7c5610a5dd3cb4002f2c5b6e
Tx public key: a00676933c04389ed23eeb05198e14e58ea482b3b29de6abe2fd09257490dff1
Timestamp: 1735774408 Timestamp [UCT]: 2025-01-01 23:33:28 Age [y:d:h:m:s]: 00:097:16:53:41
Block: 1188194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69616 RingCT/type: yes/0
Extra: 01a00676933c04389ed23eeb05198e14e58ea482b3b29de6abe2fd09257490dff102110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b929e4dc459dc7cf163b02c49fe795e18b4fd68a99011fae91c7b0ac5cb3b739 0.600000000000 1674695 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": 1188204, "vin": [ { "gen": { "height": 1188194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b929e4dc459dc7cf163b02c49fe795e18b4fd68a99011fae91c7b0ac5cb3b739" } } ], "extra": [ 1, 160, 6, 118, 147, 60, 4, 56, 158, 210, 62, 235, 5, 25, 142, 20, 229, 142, 164, 130, 179, 178, 157, 230, 171, 226, 253, 9, 37, 116, 144, 223, 241, 2, 17, 0, 0, 0, 10, 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