Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f6617f0c834b76f0d62fa4cd521a26e8cd93ec80a3d2e61341d3cb5b22fbf28

Tx prefix hash: 7685116954842a66cef737a1a146d94211fdf82b946a924c4576c68586e8ec16
Tx public key: cb496c8935cf69e84d37e1c2cb6779725a36998f47a03794633b01068f7f2092
Timestamp: 1695232634 Timestamp [UCT]: 2023-09-20 17:57:14 Age [y:d:h:m:s]: 01:160:19:17:06
Block: 852415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375978 RingCT/type: yes/0
Extra: 01cb496c8935cf69e84d37e1c2cb6779725a36998f47a03794633b01068f7f2092021100000008faf35c9c000000000000000000

1 output(s) for total of 0.919592253000 dcy

stealth address amount amount idx
00: 85cac81884b49697f49e8e133b1dc234b564d92e6b17d44f7d14696c7a412ab1 0.919592253000 1306255 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": 852425, "vin": [ { "gen": { "height": 852415 } } ], "vout": [ { "amount": 919592253, "target": { "key": "85cac81884b49697f49e8e133b1dc234b564d92e6b17d44f7d14696c7a412ab1" } } ], "extra": [ 1, 203, 73, 108, 137, 53, 207, 105, 232, 77, 55, 225, 194, 203, 103, 121, 114, 90, 54, 153, 143, 71, 160, 55, 148, 99, 59, 1, 6, 143, 127, 32, 146, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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