Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dc969cb3a8c7c4d08521a0f83d2e27c15edffeff8a57154ba22ae6071b4919f

Tx prefix hash: fa64c0718632de60c4ec830618ba2fe3f22e6a3aff271396e7839a073309f2b8
Tx public key: beb6cdc937cba41174985ba090d13846e9f20a415b9ee518bc7afc9087a97edc
Timestamp: 1694973786 Timestamp [UCT]: 2023-09-17 18:03:06 Age [y:d:h:m:s]: 01:274:12:43:59
Block: 850264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457219 RingCT/type: yes/0
Extra: 01beb6cdc937cba41174985ba090d13846e9f20a415b9ee518bc7afc9087a97edc02110000000975e3f0e9000000000000000000

1 output(s) for total of 0.934808091000 dcy

stealth address amount amount idx
00: e2391e17bb9e9423764c787f8d498cfcd89b064ec3a6cc8bde4956daff595126 0.934808091000 1303974 of 0

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": 850274, "vin": [ { "gen": { "height": 850264 } } ], "vout": [ { "amount": 934808091, "target": { "key": "e2391e17bb9e9423764c787f8d498cfcd89b064ec3a6cc8bde4956daff595126" } } ], "extra": [ 1, 190, 182, 205, 201, 55, 203, 164, 17, 116, 152, 91, 160, 144, 209, 56, 70, 233, 242, 10, 65, 91, 158, 229, 24, 188, 122, 252, 144, 135, 169, 126, 220, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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