Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07e8f91665c175faa46d7a82e69a3ca2767aa1fb8baab8c8d00f1d93ed6b8c58

Tx prefix hash: a1aeafb6565dcc969608d26b23c3e1799a6425302824b8a815665a71868a7967
Tx public key: 0d98cc43644578512aa5ea2e7f0242e6404cfc7472abd95276278a2de990c740
Timestamp: 1704353716 Timestamp [UCT]: 2024-01-04 07:35:16 Age [y:d:h:m:s]: 01:110:12:10:16
Block: 927842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340088 RingCT/type: yes/0
Extra: 010d98cc43644578512aa5ea2e7f0242e6404cfc7472abd95276278a2de990c740021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12f05f0fda5a896eb0d3fbde31ed68ad615dc46730b4395f001b2b87589aeb8f 0.600000000000 1385678 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": 927852, "vin": [ { "gen": { "height": 927842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12f05f0fda5a896eb0d3fbde31ed68ad615dc46730b4395f001b2b87589aeb8f" } } ], "extra": [ 1, 13, 152, 204, 67, 100, 69, 120, 81, 42, 165, 234, 46, 127, 2, 66, 230, 64, 76, 252, 116, 114, 171, 217, 82, 118, 39, 138, 45, 233, 144, 199, 64, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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